@mkcor OK -- added an entry. I'm wondering if we need to add CHANGELOG entries for every single patch (that seems a little excessive, especially when it's something as minor as this that doesn't affect how the package behaves at all).

For example, the CHANGELOG for Dash (https://github.com/plotly/dash/blob/master/CHANGELOG.md) is only updated for minor versions.

Ok. I think you're misinterpreting what I said. It's the other way around.

I'm only asking for a CHANGELOG entry because you bumped up the version number. Personally, I would have made this tiny change without changing versions... and all this (including WIP docs) would have been smoother and faster.

But if you go from 0.0.9 to 0.0.10 (which I don't think was necessary, I actually think it's a bit odd), somehow you have to justify it... right? I still don't understand why you bumped version number to 0.0.10, but now that you did, I'm trying to make it work somehow.

Actually, you do have to bump the version number to edit the metadata. See discussion here: pypi/warehouse#2170 (comment)

More info here: https://mail.python.org/pipermail/distutils-sig/2017-December/031826.html

Looking at the CHANGELOG for Dash, it doesn't seem related to anything major/minor/patch/rc. It looks like it's updated whenever there's a version updated, whether minor or patch or anything.

Ah, you're correct! Didn't scroll down far enough :)

That's super interesting, thanks for sharing. But here I'm not really arguing about whether to increment versions or not. Rather, I'm arguing that if you do so, then you want to document it.

Do you mind rerunning CI to get those tests to pass?